Skip to content

Update Microsoft.WindowsAppSDK to 1.8 stable#837

Open
Arlodotexe wants to merge 6 commits intomainfrom
wasdk1.8
Open

Update Microsoft.WindowsAppSDK to 1.8 stable#837
Arlodotexe wants to merge 6 commits intomainfrom
wasdk1.8

Conversation

@Arlodotexe
Copy link
Copy Markdown
Member

@Arlodotexe Arlodotexe commented Mar 30, 2026

This PR upgrades our tooling, components, and dependencies to the 1.8 version of the Windows App SDK.

The changes here have had basic builds/tests run locally, and fixes several of the build issues encountered while trying to build WASDK under the new version.

Remaining uncertainty:

  • The errors in the tooling CI are caused by a package reference to an old version of the toolkit using older versions of WADSK, particularly we noted CommunityToolkit.Common (and will check for more).

Prerequisites:

  • The PR at Upgrade WASDK from 1.6 to 1.8 Tooling-Windows-Submodule#293 needs to be merged before this PR can be closed.
  • Before we can close this PR, we'll need to use the PR nuget feed here to ship a prerelease update to any toolkit components that are referenced in the gallery by our tooling.
    • This is a recurring requirement any time we update the toolkit's dependencies, it also happened with our upgrade to 1.6.
    • Generally, this friction is being recorded for possible improvements via proper toolkit-using-toolkit tooling.

@Arlodotexe Arlodotexe added this to the 8.3 milestone Mar 30, 2026
@Arlodotexe Arlodotexe self-assigned this Mar 30, 2026
@michael-hawker
Copy link
Copy Markdown
Member

michael-hawker commented Mar 31, 2026

Wahoo! 🎉🎉

michael-hawker
michael-hawker approved these changes Mar 31, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@michael-hawker michael-hawker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving in case we decide to merge this first and update tooling after.

@Arlodotexe
Copy link
Copy Markdown
Member Author

Arlodotexe commented Mar 31, 2026 •
edited
Loading

Approving in case we decide to merge this first and update tooling after.

Tooling would be the only repo where it's safe to skip the PR feed and use the mainlatest feed, but closing this PR to move others before testing upstream carries risk.

We haven't been able to fully test Labs in CI due to the prerequisite chain here, so if we skip the PR feed (e.g. close this PR now to get tooling merged too) and use mainlatest there it'll require an entire new PR to follow-up if we missed anything.

Given that, we'll do validation via additional pushes and hop between feeds as we start to close things. Only tooling should require multiple PRs for the entire task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@michael-hawker michael-hawker michael-hawker approved these changes

Assignees

@Arlodotexe Arlodotexe

Labels

None yet

Projects

None yet

Milestone

8.3

Development

Successfully merging this pull request may close these issues.

2 participants

@Arlodotexe @michael-hawker